Facility Attributes CSV File

The source file used by the CygNet Facility Import/Export utility (FacLoad.exe) is a comma-separated values (.csv) file containing facility attributes. The Export Facility Attributes option creates a .csv file for you, which can then be edited as necessary. You can also use this option to create a sample .csv file to help prepare files for use with the utility.

The first row of the file is the header row. Each successive row under the header constitutes one facility record. Each value (or cell, if viewing the .csv file in Microsoft Excel) within a facility record row represents a facility attribute.

CSV File Columns

The facility attribute columns available for use in the .csv file are described in the following table. Required columns are noted.

Note: Column header values are case-sensitive.

Column Header	Description
site*	Name of the facility’s site This column is required. * See Note below this table.
service*	Name of the facility’s current value service This column is required. * See Note below this table.
id*	Facility ID This column is required. * See Note below this table.
is_active*	Indicates if the facility record is active * See Note below this table.
desc*	Facility description * See Note below this table.
type	Facility type Devices are assigned the type DEVICE. All other types are user-defined.
category	Facility category REMDEV— Remote device COMMDEV — Communication device EXPDEV* — Import/Export device DDSFAC — A facility that is linked to a device (but is not a device) GENFAC — A facility that resides only in the PNT SERVICE — A service-level facility. In most instances, this is the facility of a Service Monitoring Service point, such as a point to monitor the status of a CygNet service (for example, MYSITE_VHS). SITE — A site-level facility. In most instances, this is the facility of a Service Monitoring Service point, such as a point to monitor the status of a CygNet site (for example, MYSITE). * See Note below this table.
security_app	Facility security application
info0	Facility info attribute 0 The default name of this attribute in the metadata is "Facility Location"
info1	Facility info attribute 1 The default name of this attribute in the metadata is "Facility Contact"
attr0 thru attr29	Text attributes 0 through 29 (each a separate column)
table0 thru table29	Table attributes 0 through 29 (each a separate column) Each table attribute has a corresponding table (stored in the TRS) that contains the list of possible selections for the attribute. The table names are in the format SYSFCTxx, where xx represents the attribute number. For example, SYSFCT00 is the table for the table0 attribute. A table record has an entry and a description. The entry must be used when defining the attribute value in the CygNet Facility Import/Export utility (FacLoad.exe) .csv file. Ideally, use only those entries that have already been defined in the table. However, if you include an entry that has not been defined in the table, it will be added. In such cases, the entry and its description will be identical. See CygNet TRS Import/Export Utility for more information about importing and exporting table entries using the TRSLoad.exe utility. Note: When using the CygNet Facility Import/Export utility to import values for a table attribute, the value will be added to the table in the TRS (SYSFCTxx). If incorrect values are specified or if values are added in the wrong attribute in the .csv file, unwanted results can occur. When importing values for table-driven fields, the utility will try to resolve the values to the table’s current entries. If it is unable to resolve the value, it will add a new entry to the table. The text will be used as both the table Entry and Description. For example, you are using Table Attribute 7 for "State" and have defined the entries/descriptions as TX/Texas, NM/New Mexico, and OK/Oklahoma. However, your import file contains "Okla" as the state for one of its entries. The utility will add "Okla" as both the entry and description (Okla/Okla) since it doesn’t have an entry to which it can resolve. You will now have facilities that are in OK and Okla.
yes_no0 thru yes_no19	Yes/No attributes 0 through 19 (each a separate column)

Column Header

Description

site*

Name of the facility’s site

This column is required.

* See Note below this table.

service*

Name of the facility’s current value service

This column is required.

* See Note below this table.

id*

Facility ID

This column is required.

* See Note below this table.

is_active*

Indicates if the facility record is active

* See Note below this table.

desc*

Facility description

* See Note below this table.

type

Facility type

Devices are assigned the type DEVICE. All other types are user-defined.

category

Facility category

REMDEV*— Remote device
COMMDEV* — Communication device
EXPDEV* — Import/Export device
DDSFAC — A facility that is linked to a device (but is not a device)
GENFAC — A facility that resides only in the PNT
SERVICE — A service-level facility. In most instances, this is the facility of a Service Monitoring Service point, such as a point to monitor the status of a CygNet service (for example, MYSITE_VHS).
SITE — A site-level facility. In most instances, this is the facility of a Service Monitoring Service point, such as a point to monitor the status of a CygNet site (for example, MYSITE).

* See Note below this table.

security_app

Facility security application

info0

Facility info attribute 0

The default name of this attribute in the metadata is "Facility Location"

info1

Facility info attribute 1

The default name of this attribute in the metadata is "Facility Contact"

attr0 thru attr29

Text attributes 0 through 29 (each a separate column)

table0 thru table29

Table attributes 0 through 29 (each a separate column)

Each table attribute has a corresponding table (stored in the TRS) that contains the list of possible selections for the attribute. The table names are in the format SYSFCTxx, where xx represents the attribute number. For example, SYSFCT00 is the table for the table0 attribute. A table record has an entry and a description. The entry must be used when defining the attribute value in the CygNet Facility Import/Export utility (FacLoad.exe) .csv file. Ideally, use only those entries that have already been defined in the table. However, if you include an entry that has not been defined in the table, it will be added. In such cases, the entry and its description will be identical.

See CygNet TRS Import/Export Utility for more information about importing and exporting table entries using the TRSLoad.exe utility.

Note: When using the CygNet Facility Import/Export utility to import values for a table attribute, the value will be added to the table in the TRS (SYSFCTxx). If incorrect values are specified or if values are added in the wrong attribute in the .csv file, unwanted results can occur. When importing values for table-driven fields, the utility will try to resolve the values to the table’s current entries. If it is unable to resolve the value, it will add a new entry to the table. The text will be used as both the table Entry and Description.
For example, you are using Table Attribute 7 for "State" and have defined the entries/descriptions as TX/Texas, NM/New Mexico, and OK/Oklahoma. However, your import file contains "Okla" as the state for one of its entries. The utility will add "Okla" as both the entry and description (Okla/Okla) since it doesn’t have an entry to which it can resolve. You will now have facilities that are in OK and Okla.

yes_no0 thru yes_no19

Yes/No attributes 0 through 19 (each a separate column)

Note: For "category" values of device types (REMDEV, COMMDEV, or EXPDEV), the facility is owned by the Device Definition Service (DDS) rather than the Facility Service (FAC), therefore edits to certain attributes (site, service, id, is_active, desc) must be made in the DDS. See DDS-Owned Facilities for more information.